Maximum users on a server

So, I've found the techNote about the maximum number of connected users on a DOORS server (which is here: https://www-304.ibm.com/support/docview.wss?uid=swg21422306 ). Does anyone have specific info on what happens if my server hits that number? Will further users be prevented from logging on, or will it let them in and drop or idle an existing connection? I have good reason to believe that we may be at or exceeding this number, and am looking to see if I need to make a case for putting this DB onto a Linux server, rather then Windows.
SystemAdmin - Mon Aug 08 18:05:09 EDT 2011

Re: Maximum users on a server
llandale - Mon Aug 08 18:52:42 EDT 2011

I don't know but I'd believe the technote. Pre 9.2 versions appear to allow it with disater results, 9.2 won't let the 451th user log in.

It would be hard to believe that anybody would code a limit and kick someone off to let someone else in; resulting in continuous loss of data and residual module locks.

  • Louie

Re: Maximum users on a server
SystemAdmin - Tue Aug 09 08:40:17 EDT 2011

Thanks for the quick response Louie. I moved our largest server up to a 9.3 server about a month ago. We had indeed been seeing issues with lingering locks, and some data corruption, though the latter is better explained by users getting in the habit of killing the DOORS Client any time they thoguht it was taking "too long" to finish a save.

Anyone have any insight on what that 451st user gets/sees if they try to log in?

Re: Maximum users on a server
llandale - Tue Aug 09 16:14:39 EDT 2011

SystemAdmin - Tue Aug 09 08:40:17 EDT 2011
Thanks for the quick response Louie. I moved our largest server up to a 9.3 server about a month ago. We had indeed been seeing issues with lingering locks, and some data corruption, though the latter is better explained by users getting in the habit of killing the DOORS Client any time they thoguht it was taking "too long" to finish a save.

Anyone have any insight on what that 451st user gets/sees if they try to log in?

You dealing with folks who cancel during a save? lol snip numerous sarcastic replies --snip several empathetic replies --

If you have different projects that are unrelated you could easily split your database up into two databases on the same server, each with their own data directory and port. Folks would need to know which database to connect to but you can do that with two cleverly named DOORS shortcuts. It would get tricky with two sets of DOORS users, but I suspect you don't need to keep them the same and most folks will never need to go to the other database.

If you have one huge project they are all dealing with then ... you need to plead for Linux. Mentioning your plight in the 1st sentence above may get you sympathy $s.

I also infer your connection is slow; moving the server closer will make everybody's life better.

  • Louie

Re: Maximum users on a server
SystemAdmin - Wed Aug 10 11:25:29 EDT 2011

llandale - Tue Aug 09 16:14:39 EDT 2011
You dealing with folks who cancel during a save? lol snip numerous sarcastic replies --snip several empathetic replies --

If you have different projects that are unrelated you could easily split your database up into two databases on the same server, each with their own data directory and port. Folks would need to know which database to connect to but you can do that with two cleverly named DOORS shortcuts. It would get tricky with two sets of DOORS users, but I suspect you don't need to keep them the same and most folks will never need to go to the other database.

If you have one huge project they are all dealing with then ... you need to plead for Linux. Mentioning your plight in the 1st sentence above may get you sympathy $s.

I also infer your connection is slow; moving the server closer will make everybody's life better.

  • Louie

We actually have a number of servers already. This one is a monster that has resulted from a big push for reuse of common requirements. We are migrating all projects(and by that I mean Top-Level, child of the DB projects or folders) that don't link to anything else off to other servers, but they are a pretty small fraction of the use.

The slow saves are mostly realated to issues with improperly imported OLE, or more to the point - things that should have been brought in from Word as OLE, but since they were pasted into Word wrong, have been represented in the Object Text as Rich Text. This results in entries to the treedata.dtc that can run upwards of 500,000 lines. We do know how to clean this up, and have worked hard to educate users to avoid causing new issues, but with upwards of 4800 current users, and a lot of the problem Word documents coming from customers and 3rd party sources, it does still crop up.

We're keenly aware of network latency issues, and advise all users in sites outside of our central location (midwestern USA) to use Citrix to allow them to be running DOORS on a machine that is local relative to the server. (I doubt we'll get very far moving India or France closer to the midwest, or vice-versa, lol).

So I think I'll try a push for a Linux OS on this server. We're in the process of dealing with some issues of growth and storage on it anyway, and I think Linux may help with at least one of those as well.

Still interested in knowing if anyone has expereince with what the users should be seeing if they are "lucky user #451".